a test for lock performance #5
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexsku
commented
Dec 24, 2016
| { | ||
| var locked = false; | ||
| spinLock.Enter(ref locked); | ||
| if (!locked) |
Owner
Author
There was a problem hiding this comment.
never used SpinLock, i wonder when it is envisioned locked can be false?
This was referenced Jan 4, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The test illustrates how low the overhead of lock when there is no contention. This is a typical output of the test on my laptop:
Without locks took: 14.0863ms
With lock took: 39.8ms
With spinlock took: 29.7597ms
With concurrent queue took: 35.2681ms
With concurrent bag took: 156.2363ms
With concurrent dictionary took: 681.0128ms
With manual spinlock took: 19.2666ms
From these results it can be seen that using lock adds about 25 nanoseconds to the execution. which is only a little bit more than using Interlocked.CompareExchange (manual spinlock) test.
At the same time concurrent collections perform much worse when there is no contention.